home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941031-19941221
/
000211_news@columbia.edu_Mon Nov 21 08:33:25 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA20243
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 21 Nov 1994 08:33:25 -0500
Received: by apakabar.cc.columbia.edu id AA16446
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 21 Nov 1994 08:33:24 -0500
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!ee.und.ac.za!ticsa.com!soren.aztec.co.za!soren
From: soren@aztec.co.za (Soren Aalto)
Newsgroups: comp.protocols.kermit.misc,alt.winsock
Subject: Re: winsock/pkt dvr hack possible?
Date: Mon, 21 Nov 1994 15:31:44
Organization: Linkdata
Lines: 39
Message-Id: <soren.223.000F87E0@aztec.co.za>
References: <3a67j8$j39@Mercury.mcs.com> <3anvci$dut@relay.tor.hookup.net> <1994Nov20.105834.33349@cc.usu.edu> <p.waltenberg.1154.2ECFB2E0@irl.cri.nz> <3aoc2h$bit@apakabar.cc.columbia.edu>
Nntp-Posting-Host: soren.aztec.co.za
X-Newsreader: Trumpet for Windows [Version 1.0 Rev A]
Xref: news.columbia.edu comp.protocols.kermit.misc:1155 alt.winsock:22528
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3aoc2h$bit@apakabar.cc.columbia.edu> jaltman@watsun.cc.columbia.edu (Jeffrey Altman) writes:
>>> Jeff is correct. The top of a sockets API is a TCP stream channel of
>>>bytes, not packets. "It could be done..." means creating a second TCP/IP
>>>stack feeding from the streams channel and packaging it into TCP/IP over
>>>Ethernet frames to be passed to the application. Not very desirable, nor
>>>realistic.
>>> Joe D.
>>
>>Actually acheiving the required functionality is pretty trivial, just run the
>>winsock on top of a packet multiplexor on top of a packet driver instead.
>>Using packet mux on top of the packet driver you can get packet drivers for
>>DOS boxes plus a packet driver for Trumpet winsock. Pktmux can be found on
>>biochemistry.cwru.edu. (and quite a few other sites).
>>The system has to be configured at the bottom (DOS) level to use packet
>>drivers, but thats possible with nearly all configurations.
>>
>>I'll admit that going from Winsock to packet driver is nightmarish, but
>>actually acheiving whats wanted , which is KA9Q in a DOS box with Winsock
>>running isn't. Thats basically how my system is configured now.
>>
>But this doesn't address the original need.
>The original requirement was being able to run MS-DOS Kermit over a
>WinSock interface when WinSock is active over a serial line connection
>made with Windows for Workgroups.
>In this circumstance, you don't have the packet multiplexor nor the
>real packet driver for the mux to sit on.
And _that_ is the real problem. I have wondered at times if the
TCP/IP stack functionality and the Comms/SLIP/PPP functionality
shouldn't be separated into two programs--you could have a
packet driver that "reflects" stuff & attach the comms driver
for SLIP/PPP/whatever to one side and Winsock to the other.